BRC-128: SSM transport note - #168
Merged
Merged
Conversation
Collaborator
|
Merged as part of docs/BRC-128 fix, commit 1430ac5 on master. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request:
Amends or corrects an existing standard, without the need for creating a new one
Summary
BRC-128 (the Extended Format payload variant) carried no transport-mode note. Adds a Compatibility bullet stating BRC-128 frames are byte-identical on the wire under ASM and SSM, inheriting addressing and the SSM
(S,G)/source-discovery model from BRC-124 and BRC-129, with the source being the emitting proxy (senderIPv6). Adds a BRC-129 reference.